Micron Document
<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Expanded memory</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Expanded_memory"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Expanded_memory rootpage-Expanded_memory skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Expanded memory</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr">
<p class="mw-empty-elt">
</p>

<p>In <a href="DOS_memory_management" title="DOS memory management">DOS memory management</a>, <b>expanded memory</b> is a system of <a href="Bank_switching" title="Bank switching">bank switching</a> that provided additional memory to <a href="DOS" title="DOS">DOS</a> programs beyond the limit of <a href="Conventional_memory" title="Conventional memory">conventional memory</a> (640&nbsp;KiB).
</p><p><i>Expanded memory</i> is an umbrella term for several incompatible technology variants. The most widely used variant was the <b>Expanded Memory Specification</b> (<b>EMS</b>), which was developed jointly by <a href="Lotus_Software" title="Lotus Software">Lotus Software</a>, <a href="Intel" title="Intel">Intel</a>, and <a href="Microsoft" title="Microsoft">Microsoft</a>, so that this specification was sometimes referred to as "<b>LIM EMS</b>". LIM EMS had three versions: 3.0, 3.2, and 4.0. The first widely implemented version was EMS 3.2, which supported up to 8&nbsp;MiB of expanded memory and uses parts of the address space normally dedicated to communication with peripherals (<a href="Upper_memory" class="mw-redirect" title="Upper memory">upper memory</a>) to map portions of the expanded memory. <b>EEMS</b>, an expanded-memory management standard competing with LIM EMS 3.x, was developed by <a href="AST_Research" title="AST Research">AST Research</a>, <a href="Quadram" class="mw-redirect" title="Quadram">Quadram</a> and <a href="Ashton-Tate" title="Ashton-Tate">Ashton-Tate</a> ("AQA"); it could map any area of the lower 1&nbsp;MiB. EEMS ultimately was incorporated in LIM EMS 4.0, which supported up to 32&nbsp;MiB of expanded memory and provided some support for DOS multitasking as well. IBM, however, created its own expanded-memory standard called <b>XMA</b>.
</p><p>The use of expanded memory became common with games and business programs such as <a href="Lotus_1-2-3" title="Lotus 1-2-3">Lotus 1-2-3</a> in the late 1980s through the mid-1990s, but its use declined as users switched from DOS to <a href="Protected-mode" class="mw-redirect" title="Protected-mode">protected-mode</a> operating systems such as <a href="Linux" title="Linux">Linux</a>, <a href="IBM_OS/2" class="mw-redirect" title="IBM OS/2">IBM OS/2</a>, and <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a>.
</p>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="Background">Background</h2></div>

<p>The <a href="Intel_8088" title="Intel 8088">8088</a> processor of the <a href="IBM_PC" class="mw-redirect" title="IBM PC">IBM PC</a> and <a href="IBM_PC/XT" class="mw-redirect" title="IBM PC/XT">IBM PC/XT</a> can address one <a href="Megabyte" title="Megabyte">megabyte</a> (MiB, or 2<sup>20</sup> bytes) of memory. It inherited this limit from the 20-bit external address bus (and overall memory addressing architecture) of the <a href="Intel_8086" title="Intel 8086">Intel 8086</a>. The designers of the PC allocated the lower 640&nbsp;<a href="Kilobyte" title="Kilobyte">KiB</a> (<span class="nowrap">655<span style="margin-left:.25em;">360</span></span> bytes) of address space for read-write program memory (RAM), called <i>conventional memory</i>, and the remaining 384&nbsp;KiB of memory space is reserved for uses such as the system <a href="BIOS" title="BIOS">BIOS</a>, video memory, and memory on expansion peripheral boards.
</p><p>Even though the <a href="IBM_PC_AT" class="mw-redirect" title="IBM PC AT">IBM PC AT</a>, introduced in 1984, uses the <a href="80286" class="mw-redirect" title="80286">80286</a> chip that can address up to 16&nbsp;MiB of RAM as <a href="Extended_memory" title="Extended memory">extended memory</a>, it can only do so in <a href="Protected_mode" title="Protected mode">protected mode</a>. The scarcity of software compatible with protected mode (no standard <a href="DOS" title="DOS">DOS</a> applications can run in it) meant that the market was still open for another solution.<sup id="cite_ref-Mendelson_1989_1-0" class="reference"><a href="#cite_note-Mendelson_1989-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p><p>To make more memory accessible, a <a href="Bank_switching" title="Bank switching">bank switching</a> scheme was devised, where only selected parts of the additional memory is accessible at any given time. Originally, a single 64&nbsp;KiB (2<sup>16</sup> bytes) window of memory, called a <a href="Page_frame" class="mw-redirect" title="Page frame">page frame</a>, was used; later this was made more flexible. Programs are written in a specific way to access expanded memory. The <i>window</i> between conventional memory and expanded memory can be adjusted to access different locations within the expanded memory.
</p><p>A first attempt to use a bank switching technique was made by Tall Tree Systems with its JRAM boards,<sup id="cite_ref-TallTree_2-0" class="reference"><a href="#cite_note-TallTree-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> but these did not catch on.<sup id="cite_ref-Mendelson_1989_1-1" class="reference"><a href="#cite_note-Mendelson_1989-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> (Tall Tree Systems later made EMS-based boards using the same JRAM brand.)
</p>
<div class="mw-heading mw-heading2"><h2 id="Expanded_Memory_Specification_(EMS)">Expanded Memory Specification (EMS)</h2></div>
<p><a href="Lotus_Software" title="Lotus Software">Lotus Development</a>, <a href="Intel" title="Intel">Intel</a>, and <a href="Microsoft" title="Microsoft">Microsoft</a> cooperated to develop the EMS standard (aka LIM EMS). The first publicly available version of EMS, version 3.0 allows access of up to 4&nbsp;MiB of expanded memory. This was increased to 8&nbsp;MiB with version 3.2 of the specification. The final version of EMS, version 4.0 increased the maximum amount of expanded memory to 32&nbsp;MiB and supports additional functionality.
</p><p>Microsoft thought that bank switching was an inelegant and temporary, but necessary stopgap measure. Slamming his fist on the table during an interview <a href="Bill_Gates" title="Bill Gates">Bill Gates</a> said of expanded memory, "It's garbage! It's a <a href="Kludge" title="Kludge">kludge</a>! … But we're going to do it". The companies planned to launch the standard at the Spring 1985 <a href="COMDEX" title="COMDEX">COMDEX</a>, with many expansion-card and software companies announcing their support.<sup id="cite_ref-Machrone_1985_3-0" class="reference"><a href="#cite_note-Machrone_1985-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-pc200801_4-0" class="reference"><a href="#cite_note-pc200801-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> <a href="AST_Research" title="AST Research">AST Research</a>, <a href="STB_Systems" title="STB Systems">STB Systems</a>, <a href="Persyst" class="mw-redirect" title="Persyst">Persyst</a>, <a href="Quadram" class="mw-redirect" title="Quadram">Quadram</a>, and <a href="Tecmar" title="Tecmar">Tecmar</a> quickly designed EMS-compliant cards to compete with Intel's own Above Board expansion card. By mid-1985 some already called EMS a <a href="De_facto_standard" title="De facto standard">de facto standard</a>.<sup id="cite_ref-maremaa19850617_5-0" class="reference"><a href="#cite_note-maremaa19850617-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>
</p><p>The first public version of the EMS standard, called EMS 3.0 was released in 1985; EMS 3.0, however, saw almost no hardware implementations before being superseded by EMS 3.2. EMS 3.2 uses a 64&nbsp;KiB region in the upper 384&nbsp;KiB (<a href="Upper_memory" class="mw-redirect" title="Upper memory">upper memory</a> area) divided into four 16&nbsp;KiB pages, which can be used to map portions of the expanded memory.<sup id="cite_ref-Mendelson_1989_1-2" class="reference"><a href="#cite_note-Mendelson_1989-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p><p>Quadram, AST, and <a href="Ashton-Tate" title="Ashton-Tate">Ashton-Tate</a> created the Enhanced EMS (EEMS) standard. EEMS, a superset of EMS 3.2, allows any 16&nbsp;KiB region in lower RAM to be mapped to expanded memory, as long as it was not associated with interrupts or dedicated I/O memory such as network or video cards. Thus, entire programs can be switched in and out of the extra RAM. EEMS also added support for two sets of mapping registers. These features are used by early DOS multitasker software such as <a href="DESQview" title="DESQview">DESQview</a>. 1987's LIM EMS 4.0 specification incorporated practically all features of EEMS.<sup id="cite_ref-Mendelson_1989_1-3" class="reference"><a href="#cite_note-Mendelson_1989-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>
</p><p>A new feature added in LIM EMS 4.0 was that EMS boards can have multiple sets of page-mapping registers (up to 64 sets). This allows a primitive form of DOS <a href="Computer_multitasking" title="Computer multitasking">multitasking</a>. The caveat is, however, that the standard does not specify how many register sets a board should have, so there is great variability between hardware implementations in this respect.<sup id="cite_ref-Rosch_1989_6-0" class="reference"><a href="#cite_note-Rosch_1989-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>
</p><p>The Expanded Memory Specification (EMS) is the specification describing the use of expanded memory. EMS functions are accessible through software <a href="Interrupt" title="Interrupt">interrupt</a> 67h. Programs using EMS must first establish the presence of an installed expanded memory manager (EMM) by checking for a device driver with the device name <b>EMMXXXX0</b>.
</p>
<div class="mw-heading mw-heading2"><h2 id="Expanded_Memory_Adapter_(XMA)">Expanded Memory Adapter (XMA)</h2></div>
<p>IBM remained silent as the industry widely adopted the LIM standard.<sup id="cite_ref-maremaa19850617_5-1" class="reference"><a href="#cite_note-maremaa19850617-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> The company developed its own memory standard called Expanded Memory Adapter (XMA); the IBM DOS driver for it is XMAEM.SYS. Unlike EMS, the IBM expansion boards can be addressed both using an expanded memory model and as <a href="Extended_memory" title="Extended memory">extended memory</a>.<sup id="cite_ref-mskb_7-0" class="reference"><a href="#cite_note-mskb-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> The expanded memory hardware interface used by XMA boards is, however, incompatible with EMS,<sup id="cite_ref-Welch_1986_8-0" class="reference"><a href="#cite_note-Welch_1986-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> but a XMA2EMS.SYS driver provides EMS emulation for XMA boards.<sup id="cite_ref-mskb_7-1" class="reference"><a href="#cite_note-mskb-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> XMA boards were first introduced for the 1986 (revamped) models of the <a href="3270_PC" class="mw-redirect" title="3270 PC">3270 PC</a>.<sup id="cite_ref-Welch_1986_8-1" class="reference"><a href="#cite_note-Welch_1986-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="Implementations">Implementations</h2></div>
<div class="mw-heading mw-heading3"><h3 id="Expansion_boards">Expansion boards</h3></div>

<p>This insertion of a memory window into the peripheral address space could originally be accomplished only through specific expansion boards, plugged into the <a href="Industry_Standard_Architecture" title="Industry Standard Architecture">ISA</a> expansion bus of the computer. Famous 1980s expanded memory boards were <a href="AST_Research" title="AST Research">AST</a> RAMpage, IBM PS/2 80286 Memory Expansion Option, <a href="AT%26T_Corporation" title="AT&amp;T Corporation">AT&amp;T</a> Expanded Memory Adapter and the <a href="Intel" title="Intel">Intel</a> Above Board. Given the price of RAM during the period, up to several hundred dollars per MiB, and the quality and reputation of the above brand names, an expanded memory board was very expensive.
</p>
<div class="mw-heading mw-heading3"><h3 id="Motherboard_chipsets">Motherboard chipsets</h3></div>
<p>Later, some <a href="Motherboard" title="Motherboard">motherboard</a> <a href="Chipset" title="Chipset">chipsets</a> of <a href="Intel_80286" title="Intel 80286">Intel 80286</a>-based computers implemented an expanded memory scheme that did not require add-on boards, notably the <a href="NEAT_chipset" title="NEAT chipset">NEAT chipset</a>. Typically, software switches determined how much memory should be used as <i>expanded memory</i> and how much should be used as <i><a href="Extended_memory" title="Extended memory">extended memory</a></i>.
</p>
<div class="mw-heading mw-heading3"><h3 id="Device_drivers">Device drivers</h3></div>
<p>An expanded-memory board, being a hardware peripheral, needed a software <a href="Device_driver" title="Device driver">device driver</a>, which exported its services. Such a device driver was called <b>expanded-memory manager</b>. Its name was variable; the previously mentioned boards used REMM.SYS (AST), PS2EMM.SYS (IBM), AEMM.SYS (AT&amp;T) and EMM.SYS (Intel) respectively. Later, the expression became associated with software-only solutions requiring the <a href="Intel_80386" class="mw-redirect" title="Intel 80386">Intel 80386</a> processor, for example <a href="Quarterdeck_Office_Systems" title="Quarterdeck Office Systems">Quarterdeck</a>'s <a href="QEMM" title="QEMM">QEMM</a>, Qualitas' <a href="386MAX" title="386MAX">386<sup>MAX</sup></a> or the default <a href="EMM386" title="EMM386">EMM386</a> in MS-DOS, PC&nbsp;DOS and DR-DOS.
</p>
<div class="mw-heading mw-heading3"><h3 id="Software_emulation">Software emulation</h3></div>
<p>Beginning in 1986, the built-in memory management features of <a href="Intel_80386" class="mw-redirect" title="Intel 80386">Intel 80386</a> processor freely modeled the address space when running legacy real-mode software, making hardware solutions unnecessary. Expanded memory could be simulated in software.
</p><p>The first software expanded-memory <i>management</i> (emulation) program was <a href="CEMM" title="CEMM">CEMM</a>, available in September 1986 as a utility for the <a href="Compaq_Deskpro_386" title="Compaq Deskpro 386">Compaq Deskpro 386</a>. A popular and well-featured commercial solution was Quarterdeck's QEMM. A contender was Qualitas' <a href="386MAX" title="386MAX">386<sup>MAX</sup></a>. Functionality was later incorporated into <a href="MS-DOS_4.01" class="mw-redirect" title="MS-DOS 4.01">MS-DOS 4.01</a> in 1989 and into <a href="DR_DOS_5.0" class="mw-redirect" title="DR DOS 5.0">DR&nbsp;DOS 5.0</a> in 1990, as <a href="EMM386" title="EMM386">EMM386</a>.
</p><p>Software expanded-memory managers in general offered additional, but closely related functionality. Notably, they allowed using parts of the <a href="Upper_memory_area" title="Upper memory area">upper memory area</a> (UMA) (the upper 384&nbsp;KiB of real-mode address space) called <i>upper memory blocks</i> (UMBs) and provided tools for loading small programs, typically <a href="Terminate-and-stay-resident_program" title="Terminate-and-stay-resident program">terminate-and-stay-resident programs</a> inside ("LOADHI" or "LOADHIGH").
</p><p>Interaction between <a href="Extended_memory" title="Extended memory">extended memory</a>, expanded-memory emulation and DOS extenders ended up being regulated by the XMS, <a href="Virtual_Control_Program_Interface" title="Virtual Control Program Interface">Virtual Control Program Interface</a> (VCPI), <a href="DOS_Protected_Mode_Interface" title="DOS Protected Mode Interface">DOS Protected Mode Interface</a> (DPMI) and <a href="DOS_Protected_Mode_Services" title="DOS Protected Mode Services">DOS Protected Mode Services</a> (DPMS) specifications.
</p><p>Certain emulation programs, colloquially known as LIMulators, did not rely on motherboard or 80386 features at all. Instead, they reserved 64&nbsp;KiB of the base RAM for the expanded memory window, where they copied data to and from either extended memory or the hard disk when application programs requested page switches. This was programmatically easy to implement, but performance was low. This technique was offered by AboveDisk from Above Software and by several <a href="Shareware" title="Shareware">shareware</a> programs.
</p><p>It is also possible to emulate EMS by using XMS memory on 286 CPUs using 3rd party utilities like EMM286 (.SYS driver).
</p>
<div class="mw-heading mw-heading2"><h2 id="Decline">Decline</h2></div>
<p>Expanded Memory usage declined in the 1990s. New operating systems like <a href="Linux" title="Linux">Linux</a>, <a href="Windows_9x" title="Windows 9x">Windows 9x</a>, <a href="Windows_NT" title="Windows NT">Windows NT</a>, <a href="OS/2" title="OS/2">OS/2</a>, and <a href="BSD/OS" title="BSD/OS">BSD/OS</a> supported protected mode "out of the box". These and similar developments rendered Expanded Memory an obsolete concept.
</p>
<div class="mw-heading mw-heading2"><h2 id="Similar_concepts">Similar concepts</h2></div>
<p>Other platforms have implemented the same basic concept – additional memory outside of the main address space – but in technically incompatible ways:
</p>
<ul><li><a href="Expanded_storage" class="mw-redirect" title="Expanded storage">Expanded storage</a> was a feature on IBM mainframes providing additional memory outside of the main system memory, first introduced with the IBM 3090 high-end mainframe series in 1985.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> Expanded storage could not be directly addressed by applications; an MVS feature known as "window services" enabled applications to allocate movable windows to expanded storage within their own address space. There was also a "data mover" feature which could be invoked to move data between main memory (central storage) and expanded storage; later, an "Asynchronous Data Mover Facility" (ADMF) was introduced, which enabled applications to request data to be moved between the two in the background, while they performed other processing. By the mid-1990s, expanded storage had ceased to be a physically separate memory, and had become merely a logical division within the system memory enforced by firmware; but it was not until the November 2016 release of z/VM 6.4 that IBM finally removed all support for expanded storage from its mainframe operating systems.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup></li>
<li><a href="Address_Windowing_Extensions" title="Address Windowing Extensions">Address Windowing Extensions</a> (AWE) is a conceptually similar feature in Microsoft Windows, used to enable 32-bit applications to access more memory than the 2–4GB that can fit in a 32-bit address space. Although still supported by current versions of Windows, its use has been superseded by 64-bit applications, which can access &gt;4GB of memory directly.</li>
<li><a href="Virtual_memory" title="Virtual memory">Virtual memory</a> creates the illusion of available memory using, for instance, <a href="Disk_storage" title="Disk storage">disk storage</a>.</li></ul>
<div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2></div>
<ul><li><a href="Conventional_memory" title="Conventional memory">Conventional memory</a></li>
<li><a href="DOS_memory_management" title="DOS memory management">DOS memory management</a></li>
<li><a href="Extended_memory" title="Extended memory">Extended memory</a> (XMS)</li>
<li><a href="High_memory_area" title="High memory area">High memory area</a> (HMA)</li>
<li><a href="Overlay_(programming)" title="Overlay (programming)">Overlay (programming)</a></li>
<li><a href="Upper_memory_area" title="Upper memory area">Upper memory area</a> (UMA)</li>
<li><a href="Global_EMM_Import_Specification" class="mw-redirect" title="Global EMM Import Specification">Global EMM Import Specification</a> (GEMMIS)</li>
<li><a href="X86_memory_segmentation" title="X86 memory segmentation">x86 memory segmentation</a></li>
<li><a href="Address_Windowing_Extensions" title="Address Windowing Extensions">Address Windowing Extensions</a> (AWE)</li>
<li><a href="Physical_Address_Extension" title="Physical Address Extension">Physical Address Extension</a> (PAE)</li>
<li><a href="Sideways_address_space" title="Sideways address space">Sideways address space</a> on the Acorn <i>BBC Micro</i> home computer</li></ul>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */


.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}


/* end https://en.wikipedia.org/ */
</style><div class="reflist">
<div class="mw-references-wrap"><ol class="references">
<li id="cite_note-Mendelson_1989-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-Mendelson_1989_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Mendelson_1989_1-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Mendelson_1989_1-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-Mendelson_1989_1-3"><sup><i><b>d</b></i></sup></a></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */


.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}


/* end https://en.wikipedia.org/ */
</style><cite id="CITEREFMendelson1989" class="citation magazine cs1"><a href="Edward_Mendelson" title="Edward Mendelson">Mendelson, Edward</a> (1989-12-12). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=5CmkZ3THZtwC&amp;pg=PT170">"A Slot Full of RAM"</a>. <i><a href="PC_Magazine" class="mw-redirect" title="PC Magazine">PC Magazine</a></i>. Vol.&nbsp;8, no.&nbsp;21. <a href="Ziff_Davis_Publishing_Co." class="mw-redirect" title="Ziff Davis Publishing Co.">Ziff Davis Publishing Co.</a> pp.&nbsp;169–. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200208221014/https://books.google.de/books?id=5CmkZ3THZtwC&amp;lpg=PT171&amp;pg=PT170&amp;redir_esc=y">Archived</a> from the original on 2020-02-08<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-02-08</span></span>.</cite></span>
</li>
<li id="cite_note-TallTree-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-TallTree_2-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://archive.org/details/1983-talltree-brochure">"Tall Tree Systems Product Datasheet"</a> (Broschure). Tall Tree Systems. October 1983.</cite></span>
</li>
<li id="cite_note-Machrone_1985-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-Machrone_1985_3-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFMachrone1985" class="citation magazine cs1">Machrone, Bill (1985-05-14). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=DDlmJxSURq8C&amp;pg=PA33">"Memory Scheme Breaks 640K"</a>. <i><a href="PC_Magazine" class="mw-redirect" title="PC Magazine">PC Magazine</a></i>. Vol.&nbsp;4, no.&nbsp;10. <a href="Ziff_Davis_Publishing_Co." class="mw-redirect" title="Ziff Davis Publishing Co.">Ziff Davis Publishing Co.</a> p.&nbsp;33<span class="reference-accessdate">. Retrieved <span class="nowrap">2013-10-28</span></span>.</cite></span>
</li>
<li id="cite_note-pc200801-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-pc200801_4-0">^</a></b></span> <span class="reference-text"><cite class="citation magazine cs1"><a rel="nofollow" class="external text" href="https://books.google.com/books?id=Gr8rWafdWZAC&amp;pg=PA88">"The Most Memorable Tech Flops"</a>. <i>PC Magazine</i>. January 2008. pp.&nbsp;<span class="nowrap">88–</span>89<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-09-05</span></span>.</cite></span>
</li>
<li id="cite_note-maremaa19850617-5"><span class="mw-cite-backlink">^ <a href="#cite_ref-maremaa19850617_5-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-maremaa19850617_5-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFMaremaa1985" class="citation magazine cs1">Maremaa, Tom (1985-06-17). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=FS8EAAAAMBAJ&amp;pg=PA30">"Board Makers Flock to New Standard"</a>. <i>InfoWorld</i>. Vol.&nbsp;7, no.&nbsp;24. pp.&nbsp;<span class="nowrap">30–</span>34<span class="reference-accessdate">. Retrieved <span class="nowrap">2025-05-01</span></span>.</cite></span>
</li>
<li id="cite_note-Rosch_1989-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-Rosch_1989_6-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFRosch1989" class="citation magazine cs1">Rosch, Winn L. (1989-12-12). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=5CmkZ3THZtwC&amp;pg=PT175">"EMS 4.0: The Standard That Wasn't"</a>. <i><a href="PC_Magazine" class="mw-redirect" title="PC Magazine">PC Magazine</a></i>. Vol.&nbsp;8, no.&nbsp;21. <a href="Ziff_Davis_Publishing_Co." class="mw-redirect" title="Ziff Davis Publishing Co.">Ziff Davis Publishing Co.</a> pp.&nbsp;<span class="nowrap">174–</span>175. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200208220433/https://books.google.de/books?id=5CmkZ3THZtwC&amp;pg=PT175&amp;redir_esc=y">Archived</a> from the original on 2020-02-08<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-02-08</span></span>.</cite></span>
</li>
<li id="cite_note-mskb-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-mskb_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-mskb_7-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20121022062051/http://support.microsoft.com/kb/37242">"A General Tutorial on the Various Forms of Memory"</a>. <a href="Microsoft" title="Microsoft">Microsoft</a>. Archived from <a rel="nofollow" class="external text" href="http://support.microsoft.com/kb/37242">the original</a> on 2012-10-22.</cite></span>
</li>
<li id="cite_note-Welch_1986-8"><span class="mw-cite-backlink">^ <a href="#cite_ref-Welch_1986_8-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Welch_1986_8-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFWelch1986" class="citation news cs1">Welch, Marc J. (1986-04-14). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=OS8EAAAAMBAJ&amp;pg=PA5">"3270 Demand Not Expected To Rise"</a>. <i><a href="InfoWorld" title="InfoWorld">InfoWorld</a></i>. Vol.&nbsp;8, no.&nbsp;15. <a href="InfoWorld_Media_Group%2C_Inc." class="mw-redirect" title="InfoWorld Media Group, Inc.">InfoWorld Media Group, Inc.</a> p.&nbsp;5. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a>&nbsp;<a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0199-6649">0199-6649</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200208215655/https://books.google.de/books?id=OS8EAAAAMBAJ&amp;pg=PA6&amp;lpg=PA5&amp;focus=viewport&amp;hl=de">Archived</a> from the original on 2020-02-08<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-02-08</span></span>.</cite></span>
</li>
<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFSakakiSamukawaHonjou1988" class="citation journal cs1">Sakaki, M.; Samukawa, H.; Honjou, N. (1988). <span class="id-lock-subscription" title="Paid subscription required"><a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/5387596">"Effective utilization of IBM 3090 large virtual storage in the numerically intensive computations of ab initio molecular orbitals"</a></span>. <i>IBM Systems Journal</i>. <b>27</b> (4): <span class="nowrap">528–</span>540. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1147%2Fsj.274.0528">10.1147/sj.274.0528</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a>&nbsp;<a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0018-8670">0018-8670</a>.</cite></span>
</li>
<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.vm.ibm.com/perf/tips/storconf.html">"IBM: Configuring Storage"</a>. <i>www.vm.ibm.com</i>. 2006-08-29<span class="reference-accessdate">. Retrieved <span class="nowrap">2023-05-03</span></span>.</cite></span>
</li>
</ol></div></div>
<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>
<ul><li><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.phatcode.net/res/218/files/limems40.txt">"Expanded Memory Specification"</a>. Version 4.0. <a href="Lotus_Software" title="Lotus Software">Lotus</a>, <a href="Intel" title="Intel">Intel</a>, <a href="Microsoft" title="Microsoft">Microsoft</a>. October 1987. 300275-005. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200208213626/http://www.phatcode.net/res/218/files/limems40.txt">Archived</a> from the original on 2020-02-08<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-02-08</span></span>.</cite></li>
<li><cite id="CITEREFTischer1989" class="citation book cs1">Tischer, Michael (1989). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/PC_System_Programming"><i>PC System Programming for Developers</i></a></span>. Abacus. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&nbsp;<bdi>1-55755-036-0</bdi>.</cite></li>
<li><cite id="CITEREFBorrett1989" class="citation web cs1">Borrett, Lloyd Robert (January–February 1989). <a rel="nofollow" class="external text" href="http://www.borrett.id.au/computing/art-1989-01-02.htm">"Understanding EMS 4.0"</a>. <i>Technical Cornucopia</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200208213504/http://www.borrett.id.au/computing/art-1989-01-02.htm">Archived</a> from the original on 2020-02-08<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-02-08</span></span>.</cite></li></ul></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2025-07-06" href="https://en.wikipedia.org/wiki/?title=Expanded_memory&amp;oldid=1299148896">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>

</body></html>